Search capability enhancement in service oriented architecture (SOA) service registry system

ABSTRACT

A method for searching a web service registry system by use of a search controller. A first search of a service registry program product is performed with a service name received by the search controller from a user. It is determined that the received service name does not have a service description associated with the received service name in the service registry program product. A second search of the service registry program product is coordinated with a candidate service name by use of the search module, wherein the candidate service name is semantically and syntactically interchangeable with the received service name such that the candidate service name identifies the service description associated with the received service name within the service registry program product. The service description is discovered to be associated with the candidate service name within the service registry program product and is subsequently returned to the user.

This application is a continuation application claiming priority to Ser. No. 12/945,151, filed Nov. 12, 2010.

CROSS-REFERENCE TO RELATED APPLICATIONS

This invention is related to U.S. patent application Ser. No. 12/174,944 entitled “SYSTEM AND METHOD FOR PERFORMING ADVANCED SEARCH IN SERVICE REGISTRY SYSTEM”, filed on Jul. 17, 2008, and U.S. patent application Ser. No. 12/175,552 entitled “SYSTEM AND METHOD FOR IMPROVING NON-EXACT MATCHING SEARCH IN SERVICE REGISTRY SYSTEM WITH CUSTOM DICTIONARY”, filed on Jul. 18, 2008.

BACKGROUND OF THE INVENTION

Aspects of present invention disclose a system and associated method for automatically performing advanced searches for a service description by use of a search controller in a service-oriented architecture (SOA) service registry system. Conventional SOA service registry systems require users to provide an exact service name to search for a specific service description published in a registry of the SOA registry system. Also, because conventional SOA service registry systems have tightly coupled processing components, it is difficult to improve functionality and/or performance of conventional SOA service registry systems in a scalable fashion.

BRIEF SUMMARY

According to one embodiment of the present invention, a method for searching a web service registry system by use of a search controller, the method comprises: the search controller receiving a service name from a user of the web service registry system, wherein the web service registry system comprises the search controller, a service registry, a name parser, a dictionary, and a name composer, and wherein the service registry comprises at least one service description searchable by a respectively associated service name; performing a first search of the service registry with the received service name and subsequently determining that the received service name does not have a service description associated with the received service name in the service registry; coordinating a second search of the service registry with a candidate service name by use of the name parser, the dictionary, and the name composer, wherein the candidate service name is semantically and syntactically interchangeable with the received service name such that the candidate service name identifies the service description associated with the received service name within the service registry; and discovering the service description is associated with the candidate service name within the service registry and subsequently returning the discovered service description to the user of the web service registry system.

According to one embodiment of the present invention, a computer program product comprises a computer readable memory unit that embodies a computer readable program code. The computer readable program code contains instructions that, when run by a processor of a computer system, implement a method for searching a web service registry system by use of a search controller.

According to one embodiment of the present invention, a computer system comprises a processor and a computer readable memory unit coupled to the processor, wherein the computer readable memory unit containing instructions that, when run by the processor, implement a method for searching a web service registry system by use of a search controller.

According to one embodiment of the present invention, a process for supporting computer infrastructure, said process comprising providing at least one support service for at least one of creating, integrating, hosting, maintaining, and deploying computer-readable code in a computing system, wherein the code in combination with the computing system is capable of performing a method for searching a web service registry system by use of a search controller.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

FIG. 1 illustrates a system for searching a web service registry system in an integrated development environment (IDE), in accordance with embodiments of the present invention.

FIGS. 2A, 2B and 2C illustrate embodiments of the service oriented architecture (SOA) registry system of FIG. 1.

FIG. 3 is a flowchart depicting a method for searching a web service registry system in the integrated development environment (IDE) of FIG. 1, as performed by the search controller, in accordance with the embodiments of the present invention.

FIG. 4 is an example listing of a service oriented architecture (SOA) service description written in the Web Services Description Language (WSDL), in accordance with the embodiments of the present invention.

FIG. 5 illustrates a computer system used for searching a web service registry system in an integrated development environment (IDE), in accordance with the embodiments of the present invention.

DETAILED DESCRIPTION

FIG. 1 illustrates a system 10 for searching a web service registry system in an integrated development environment (IDE) 12, in accordance with embodiments of the present invention.

The system 10 comprises a user 11 and the IDE 12 in which the user 11 is developing a service-oriented architecture (SOA) business application 17 and/or a software project comprising the SOA business application 17. In this specification, terms “SOA service,” “web service,” and “service” are used interchangeably.

The SOA business application 17 utilizes at least one SOA service registry entry {service name, service description}, in which each service name uniquely identifies a respective service description. Each service description comprises information necessary to provide a SOA service identified by a respective service name within each SOA service registry entry.

The IDE 12 comprises an IDE user interface 13 and a service-oriented architecture (SOA) service registry system 20. Examples of the IDE user interface 13 may be, inter alia, application programming interface (API), a user interface to receive a web service name to search an associated web service description, and combinations thereof. The SOA service registry system 20 comprises said at least one SOA service registry entry {service name, service description} and components facilitating a search of a service description 15 by user of a service name 14 that is associated with the service description 15 in a particular service registry entry. The SOA service registry system 20 is configured to look up the service description 15 with a service name 14 provided by the user 11. See FIGS. 2A, 2B, and 2C, infra, for embodiments of the SOA service registry system 20.

The user 11 provides the service name 14 as an input to the SOA service registry system 20 through the IDE user interface 13 to search the service description 15 corresponding to the service name 14. The user 11 receives the service description 15 comprising a service name value that matches the service name 14 if the service description 15 is found in the SOA service registry system 20. The user 11 receives a null wherein no service description comprising a service name value that matches the service name 14 is found in the web service registry system 20. See descriptions of FIG. 3, infra, for detailed search operations.

The service description 15 comprises development time information, a communication protocol and a message format. An example of the development time information may be, inter alia, operations exposed by a given service, etc. Examples of the communication protocol may be, inter alia, the Hypertext Transfer Protocol (HTTP), Internet Inter-Orb Protocol (HOP), Java Remote Method Protocol (JRMP), Java Message Service (JMS) protocol, etc. An example of the message format may be, inter alia, the Simple Object Access Protocol (SOAP), etc. The service description 15 further comprises runtime information such as the IP address and port number for a given service implementation. Web Service Description Language (WSDL) is usually employed to describe a SOA service. See FIG. 4, infra, for an example of the service description for a SOA service registry entry written in Web Services Description Language (WSDL) format.

The SOA service registry system 20 comprises a service registry, a name parser, a dictionary, a name composer, a search controller, and a SOA service registry user interface. The service registry is used to publish service descriptions and to search published service descriptions with a respective service name. See descriptions of FIGS. 2A, 2B, and 2C, infra, for each component and interactions among the components in various configuration of the SOA service registry system 20.

FIG. 2A illustrates a first embodiment of the service oriented architecture (SOA) registry system 20A of FIG. 1, supra.

The first SOA service registry system 20A comprises a service registry 21, a name parser 22, a dictionary 23, a name composer 24, a search controller 25, and a SOA service registry system interface 26. The first SOA service registry system 20A embodies the most generic configuration of a SOA registry system that provides advanced search capability, wherein a service name can be matched to identical and/or similar service name that had been provided by a user. In conventional SOA registry systems, search capability is limited and a service name identifying a service description needs to be identical to a service name given by a user to find a match.

The service registry 21 receives the service name 14 from the search controller 25 and returns the service description 15 to the search controller 25 if the service description 15 matching the service name 14 exists in the service registry 21. The service registry 21 also receives candidate service names generated by the name composer 24 from the search controller 25 and returns service descriptions found as matching the candidate service names existing in the service registry 21. The service registry 21 stores said at least one service description utilized in the SOA business application 17 of FIG. 1, supra, which is searchable by a respective service name. The service registry 21 utilizes the service name 14 as a key to search the service registry entries for the service description 15 associated with the service name 14. The service registry 21 may be implemented by used of a conventional SOA service registry system, enabling the advanced search functionality described in this specification for such conventional SOA service registry system.

The name parser 22 receives the service name 14 from the search controller 25. The name parser 22 generates a component word list from the service name 14, which comprises at least one word constitutes the service name 14. Each word is distinguished according to a shortest meaningful word listed in conventional dictionaries. For example, when the service name is “globalWeatherService”, the name parser 22 generates the component word list {global, weather, service}, as shown in FIG. 4, infra. The name parser 22 returns the component word list to the search controller 25.

The dictionary 23 receives the component word list from the search controller 25. The dictionary 23 generates a respective synonym list for each word in the component word list generated by the name parser 22. The dictionary 23 returns the synonym list for each component word to the search controller 25.

The name composer 24 receives all synonym lists from the search controller 25. The name composer 24 generates a candidate service name list from the received synonym lists generated by the dictionary 23 such that the candidate service name list comprises at least one candidate service name that is not identical to the service name 14 but has a meaning similar to the service name 14.

The search controller 25 coordinates interactions among the service registry 21, the name parser 22, the dictionary 23, and the name composer 24 in performing advanced search with the service name 14 in the first SOA service registry system 20A. The search controller 25 provides a respective internal interface for the service registry 21, the name parser 22, the dictionary 23, and the name composer 24 in employing each component of the first SOA service registry system 20A. Since components of the first SOA service registry system 20A are loosely coupled by use of the search controller 25, the first SOA service registry system 20A may employ any implementation of the components if such implementation has application programming interface (API) specified. Consequently, the search controller 25 modularizes components of the first SOA service registry system 20A. Each component may be independently modified wherein the search controller 25 provides proper interface and coordination according to the modified component. See descriptions of FIG. 3, infra, for detailed operations of the search controller 25.

The SOA service registry system interface 26 is an external communication channel for the first SOA service registry system 20A through which the first SOA service registry system 20A communicates with the user of the IDE in FIG. 1 supra or other program components utilized in the SOA business application in FIG. 1 supra. Examples of the SOA service registry system interface 26 may be, inter alia, a combination of an input prompt for the service name 14 and an output display of the service description 15, an application programming interfaces (APIs) for other program components, etc.

FIG. 2B illustrates a second embodiment of the service oriented architecture (SOA) registry system 20 of FIG. 1, supra.

The second SOA service registry system 20B comprises a search module 30A, a conventional service registry program product 31, and a SOA service registry system interface 26. The second SOA service registry system 20B embodies a configuration improving search capability of the conventional service registry program product 31, wherein the service name 14 can be matched to service names with similar meanings even if there is no exact match for the service name 14 within the conventional service registry program product 31.

The search module 30A comprises a name parser 32, a dictionary 33, a name composer 34, and a search controller 35. See descriptions of FIG. 2A supra for details of the name parser 32, the dictionary 33, and the name composer 34.

The search controller 35 coordinates internal and external interactions among the conventional service registry program product 31 and components of the search module 30A in performing advanced search with the service name 14 in the second SOA service registry system 20B. The search controller 35 provides a respective internal interface for the name parser 32, the dictionary 33, and the name composer 34 in employing each component of the second SOA service registry system 20B. The search controller 35 also provides a seamless interface with the conventional service registry program product 31 for all components of the search module 30A. See descriptions of FIG. 3, infra, for detailed operations of the search controller 35.

The conventional service registry program product 31 receives the service name 14 and/or the candidate service names from the search controller 35 and returns the service description 15 that found to be matching to the received service name(s) to the search controller 25 if the service description 15 exists among entries of the conventional service registry program product 31.

FIG. 2C illustrates a third embodiment of the service oriented architecture (SOA) registry system 20 of FIG. 1, supra.

The third SOA service registry system 20C comprises a search module 30B, a SOA service registry system interface 26, a conventional service registry program product 41, and a conventional dictionary program product 43. The third SOA service registry system 20C embodies a configuration improving search capability of the conventional service registry program product 41, wherein the service name 14 can be matched to candidate service names with similar meanings even if there is no exact match for the service name 14 within the conventional service registry program product 41, by use of the conventional dictionary program product 43 in generating the candidate service names.

The search module 30B comprises a name parser 42, a name composer 44, and a search controller 45. See descriptions of FIG. 2A supra for details of the name parser 42 and the name composer 44.

The search controller 45 coordinates internal and external interactions among the search module 30B, the conventional service registry program product 41, and the conventional dictionary program product 43 in performing advanced search with the service name 14 in the third SOA service registry system 20C. The search controller 45 provides a respective internal interface for the name parser 52 and the name composer 54 within the search module 30B. The search controller 45 provides a respective external interface between the conventional service registry program product 41 and the search module 30B as well as between the conventional dictionary program product 43 and the search module 30B. See descriptions of FIG. 3, infra, for detailed operations of the search controller 35.

The conventional dictionary program product 43 is particularly useful when generic terms are employed in the service name 14 and the third SOA service registry system 20C is used to generate extensive candidate service names for advanced search functionality. See descriptions of FIG. 2B, supra, for details of the conventional service registry program product 41.

FIG. 3 is a flowchart depicting a method for searching a web service registry system in the integrated development environment (IDE) of FIG. 1, supra, as performed by the search controller, in accordance with the embodiments of the present invention.

In step 110, the search controller receives a service name from a user through the user interface. In the following steps 120 to 170, the search controller looks for a service description comprising a service name value that matches the received service name. In this specification, the service description stored in the registry has zero or more data field other than a service name field. Also in this specification, wherein a value of a service name field within a service description is identical to a first service name, the service description is referred to as being matched to the first service name. Then the search controller proceeds with step 120.

In step 120, the search controller searches the registry for the received service name and determines whether the service description that is matched to the received service name has been found in the registry. If the search controller determines that a matching service description of the received service name has been found in the registry, then the search controller proceeds with step 180. If the search controller determines that the matching service description of the received service name has not been found in the registry, then the search controller proceeds with step 130 to perform a series of searches based on the received service name.

In step 130, the search controller sends the service name received in step 110 to the name parser and receives a constituent word list comprising at least one constituent word of the received service name as parsed by the name parser as a result. See U.S. Patent applications listed in the CROSS-REFERENCE TO RELATED APPLICATIONS section, supra, for detailed operations of the name parser. Then the search controller proceeds with step 140.

In step 140, the search controller sends the constituent word list received in step 130 to the dictionary and receives at least one synonym list for each constituent word in the constituent word list as generated by the dictionary as a result. See U.S. Patent applications listed in the CROSS-REFERENCE TO RELATED APPLICATIONS section, supra, for detailed operations of the dictionary. Then the search controller proceeds with step 150.

In step 150, the search controller sends said at least one synonym list received in step 140 to the name composer and receives an alternative service name list comprising at least one alternative service name as a result. See U.S. Patent applications listed in the CROSS-REFERENCE TO RELATED APPLICATIONS section, supra, for detailed operations of the name composer.

For each alternative service name in the alternative service name list received in step 150 supra, the search controller performs steps 160 and 170. Said each alternative service name is semantically similar to the received service name. The search controller selects a first alternative service name as a current alternative service name and proceeds with step 160.

In step 160, the search controller searches the registry for the current alternative service name and determines whether a service description matching the current alternative service name has been found in the registry. If the search controller determines that the service description matching the current alternative service name has been found in the registry, the search controller proceeds with step 170. If the search controller determines that the service description matching the current alternative service name has not been found in the registry, the search controller repeats step 160 with a next alternative service name from the alternative service name list. If no service description matching any alternative service name has been found upon performing step 160 for all alternative service names in the alternative service name list, the search controller proceeds with step 190.

In step 170, because the service description matching the current alternative service name has been found in the registry, the search controller returns the found service description to user. The search controller subsequently terminates processing the search request for the service name received in step 110.

In step 180, because the service description matching the service name received in step 110 has been found in the registry without the advanced search, the search controller returns the service description matching the received service name to user. Then the search controller terminates processing the search request for the service name received in step 110.

In step 190, because there is no service description in the registry that matches any alternative service name in the alternative service name list generated by the name composer, the search controller returns null to user. Then the search controller terminates processing the search request for the service name received in step 110.

FIG. 4 is an example listing of a service oriented architecture (SOA) service description written in the Web Services Description Language (WSDL), in accordance with the embodiments of the present invention.

In lines L101 through L105, various namespaces are declared. In lines L106 through L125, various data types are declared. In lines L126 through L131, message types are declared, which consist of an input message type and an output message type. In lines 132 through L137, various operations included in the web service are declared.

FIG. 5 illustrates a computer system 90 used for searching a web service registry system in an integrated development environment (IDE), in accordance with the embodiments of the present invention.

The computer system 90 comprises a processor 91, an input device 92 coupled to the processor 91, an output device 93 coupled to the processor 91, and memory devices 94 and 95 each coupled to the processor 91. In this specification, the computer system 90 represents any type of programmable data processing apparatus.

The input device 92 is utilized to receive input data 96 into the computer system 90. The input device 92 may be, inter alia, a keyboard, a mouse, a keypad, a touch screen, a scanner, a voice recognition device, a sensor, a network interface card (NIC), a Voice/video over Internet Protocol (VoIP) adapter, a wireless adapter, a telephone adapter, a dedicated circuit adapter, etc. The output device 93 is utilized to communicate results generated by the computer program code 97 to a user of the computer system 90. The output device 93 may be, inter alia, a printer, a plotter, a computer screen, a magnetic tape, a removable hard disk, a floppy disk, a NIC, a VoIP adapter, a wireless adapter, a telephone adapter, a dedicated circuit adapter, an audio and/or visual signal generator, a light emitting diode (LED), etc.

Any of the components of the present invention can be deployed, managed, serviced, etc. by a service provider that offers to deploy or integrate computing infrastructure with respect to a process for performing a series of searches of the web service registry system of the present invention. Thus, the present invention discloses a process for supporting computer infrastructure, comprising integrating, hosting, maintaining and deploying computer-readable code into a computing system (e.g., computing system 90), wherein the code in combination with the computing system is capable of performing a method for searching the web service registry system.

In another embodiment, the invention provides a business method that performs the process steps of the invention on a subscription, advertising and/or fee basis. That is, a service provider, such as a Solution Integrator, can offer to create, maintain, support, etc., a process for searching the web service registry system of the present invention. In this case, the service provider can create, maintain, support, etc. a computer infrastructure that performs the process steps of the invention for one or more customers. In return, the service provider can receive payment from the customer(s) under a subscription and/or fee agreement, and/or the service provider can receive payment from the sale of advertising content to one or more third parties.

While FIG. 5 shows the computer system 90 as a particular configuration of hardware and software, any configuration of hardware and software, as would be known to a person of ordinary skill in the art, may be utilized for the purposes stated supra in conjunction with the particular computer system 90 of FIG. 5. For example, the memory devices 94 and 95 may be portions of a single memory device rather than separate memory devices.

As will be appreciated by one skilled in the art, aspects of the present invention may be embodied as a system, method or computer program product. Accordingly, aspects of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, aspects of the present invention may take the form of a computer program product embodied in one or more computer readable medium(s) having computer readable program code embodied thereon.

Any combination of one or more computer readable medium(s) may be utilized. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. In this specification, the term “memory device” 94, 95 represent a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.

Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

Computer program code 97 for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The computer program code 97 may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).

Aspects of the present invention are described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. The term “computer program instructions” is interchangeable with the term “computer program code” 97 in this specification. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer readable storage medium that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the computer readable storage medium produce an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.

The computer program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The corresponding structures, materials, acts, and equivalents of all means or step plus function elements in the claims are intended to include any structure, material, or act for performing the function in combination with other claimed elements as specifically claimed. The description of the present invention has been presented for purposes of illustration and description, but is not intended to be exhaustive or limited to the invention in the form disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the invention. The embodiment was chosen and described in order to best explain the principles of the invention and the practical application, and to enable others of ordinary skill in the art to understand the invention for various embodiments with various modifications as are suited to the particular use contemplated. 

What is claimed is:
 1. A method for searching a web service registry system by use of a search controller, said method comprising: performing, by a processor of a computer system, a first search of a service registry program product with a service name received by the search controller from a user of the web service registry system, wherein the web service registry system comprises a search module and the service registry program product, wherein the search module comprises the search controller, a name parser, a dictionary, and a name composer, and wherein the service registry program product comprises at least one service description searchable by a respectively associated service name; after said performing the first search, said processor determining that the received service name does not have a service description associated with the received service name in the service registry program product; said processor coordinating a second search of the service registry program product with a candidate service name by use of the search module, wherein the candidate service name is semantically and syntactically interchangeable with the received service name such that the candidate service name identifies the service description associated with the received service name within the service registry program product; and said processor discovering that the service description is associated with the candidate service name within the service registry program product and subsequently returning the discovered service description to the user, said coordinating comprising: sending the received service name to the name parser and subsequently receiving a component word list from the name parser, wherein the component word list comprises all words constituting the received service name; sending the component word list to the dictionary and subsequently receiving a respective synonym list for each word in the component word list from the dictionary, wherein the respective synonym list comprises at least one synonym of said each word in the component word list; sending the respective synonym list to the name composer and subsequently receiving the candidate service name from the name composer; and sending a second search request for the service description associated with the candidate service name to the service registry program product and subsequently receiving the service description in response to the second search request.
 2. The method of claim 1, said performing the first search comprising: sending a first search request for the service description associated with the received service name to the service registry program product; and receiving a null from the service registry program product in response to the first search request, wherein the service registry program product returns the null upon failing to find the service description associated with the received service name.
 3. The method of claim 1, wherein the received service description is employed in the SOA business application that provides a service described in the received service description.
 4. The method of claim 1, wherein the service description comprises elements selected from the group consisting of development time information, a communication protocol, a message format, runtime information, and combinations thereof, wherein the development time information is selected from the group consisting of a first set of operations exposed by the service name and a second set of operations exposed by the candidate service name, wherein the communication protocol is selected from the group consisting of the Hypertext Transfer Protocol (HTTP), the Internet Inter-Orb Protocol (HOP), the Java Remote Method Protocol (JRMP), and the Java Message Service (JMS) protocol, wherein the message format comprises the Simple Object Access Protocol (SOAP), wherein the runtime information is selected from the group consisting of the Internet Protocol (IP) address, a port number for the service description, and combinations thereof, and wherein the service description is represented in the Web Service Description Language (WSDL) format.
 5. The method of claim 1, said method further comprising: providing at least one support service for at least one of creating, integrating, hosting, maintaining, and deploying computer-readable program code in the computer system, said program code being executed by the processor to implement: said performing the first search; said determining that the received service name does not have a service description associated with the received service name in the service registry program product; said coordinating the second search; said discovering that the service description is associated with the candidate service name within the service registry program product; and said returning the discovered service description to the user.
 6. A computer program product comprising: a computer readable hardware storage device having a computer readable program code embodied therein, said computer readable program code containing instructions that, upon being executed by a processor of a computer system, perform a method of searching a web service registry system by use of a search controller, said method comprising: said processor performing a first search of a service registry program product with a service name received by the search controller from a user of the web service registry system, wherein the web service registry system comprises a search module and the service registry program product, wherein the search module comprises the search controller, a name parser, a dictionary, and a name composer, and wherein the service registry program product comprises at least one service description searchable by a respectively associated service name; after said performing the first search, said processor determining that the received service name does not have a service description associated with the received service name in the service registry program product; said processor coordinating a second search of the service registry program product with a candidate service name by use of the search module, wherein the candidate service name is semantically and syntactically interchangeable with the received service name such that the candidate service name identifies the service description associated with the received service name within the service registry program product; and said processor discovering that the service description is associated with the candidate service name within the service registry program product and subsequently returning the discovered service description to the user, said coordinating comprising: sending the received service name to the name parser and subsequently receiving a component word list from the name parser, wherein the component word list comprises all words constituting the received service name; sending the component word list to the dictionary and subsequently receiving a respective synonym list for each word in the component word list from the dictionary, wherein the respective synonym list comprises at least one synonym of said each word in the component word list; sending the respective synonym list to the name composer and subsequently receiving the candidate service name from the name composer; and sending a second search request for the service description associated with the candidate service name to the service registry program product and subsequently receiving the service description in response to the second search request.
 7. The computer program product of claim 6, said performing the first search comprising: sending a first search request for the service description associated with the received service name to the service registry program product; and receiving a null from the service registry program product in response to the first search request, wherein the service registry program product returns the null upon failing to find the service description associated with the received service name.
 8. The computer program product of claim 6, wherein the received service description is employed in the SOA business application that provides a service described in the received service description.
 9. The computer program product of claim 6, wherein the service description comprises elements selected from the group consisting of development time information, a communication protocol, a message format, runtime information, and combinations thereof, wherein the development time information is selected from the group consisting of a first set of operations exposed by the service name and a second set of operations exposed by the candidate service name, wherein the communication protocol is selected from the group consisting of the Hypertext Transfer Protocol (HTTP), the Internet Inter-Orb Protocol (HOP), the Java Remote Method Protocol (JRMP), and the Java Message Service (JMS) protocol, wherein the message format comprises the Simple Object Access Protocol (SOAP), wherein the runtime information is selected from the group consisting of the Internet Protocol (IP) address, a port number for the service description, and combinations thereof, and wherein the service description is represented in the Web Service Description Language (WSDL) format.
 10. A computer system comprising a processor and a computer readable memory unit coupled to the processor, said computer readable memory unit containing instructions that when executed by the processor implement a method for searching a web service registry system by use of a search controller, said method comprising: said processor performing a first search of a service registry program product with a service name received by the search controller from a user of the web service registry system, wherein the web service registry system comprises a search module and the service registry program product, wherein the search module comprises the search controller, a name parser, a dictionary, and a name composer, and wherein the service registry program product comprises at least one service description searchable by a respectively associated service name; after said performing the first search, said processor determining that the received service name does not have a service description associated with the received service name in the service registry program product; said processor coordinating a second search of the service registry program product with a candidate service name by use of the search module, wherein the candidate service name is semantically and syntactically interchangeable with the received service name such that the candidate service name identifies the service description associated with the received service name within the service registry program product; and said processor discovering that the service description is associated with the candidate service name within the service registry program product and subsequently returning the discovered service description to the user, said coordinating comprising: sending the received service name to the name parser and subsequently receiving a component word list from the name parser, wherein the component word list comprises all words constituting the received service name; sending the component word list to the dictionary and subsequently receiving a respective synonym list for each word in the component word list from the dictionary, wherein the respective synonym list comprises at least one synonym of said each word in the component word list; sending the respective synonym list to the name composer and subsequently receiving the candidate service name from the name composer; and sending a second search request for the service description associated with the candidate service name to the service registry program product and subsequently receiving the service description in response to the second search request.
 11. The computer system of claim 10, said performing the first search comprising: sending a first search request for the service description associated with the received service name to the service registry program product; and receiving a null from the service registry program product in response to the first search request, wherein the service registry program product returns the null upon failing to find the service description associated with the received service name.
 12. The computer system of claim 10, wherein the received service description is employed in the SOA business application that provides a service described in the received service description.
 13. The computer system of claim 10, wherein the service description comprises elements selected from the group consisting of development time information, a communication protocol, a message format, runtime information, and combinations thereof, wherein the development time information is selected from the group consisting of a first set of operations exposed by the service name and a second set of operations exposed by the candidate service name, wherein the communication protocol is selected from the group consisting of the Hypertext Transfer Protocol (HTTP), the Internet Inter-Orb Protocol (HOP), the Java Remote Method Protocol (JRMP), and the Java Message Service (JMS) protocol, wherein the message format comprises the Simple Object Access Protocol (SOAP), wherein the runtime information is selected from the group consisting of the Internet Protocol (IP) address, a port number for the service description, and combinations thereof, and wherein the service description is represented in the Web Service Description Language (WSDL) format. 